This repository has been archived by the owner on Nov 9, 2021. It is now read-only.
added ability to configure the Markdown parser #111
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I really like Phrozn, but wanted to make it easier to use Google Prettify within Markdown. It's possible to configure the Markdown parser to include the required 'prettyprint' class on the
<pre>
tag, but there was no way to do that within Phrozn.This pull request corrects that. It's a fairly simple change only to the Markdown processor to look for likely configuration settings in both the front matter and the sitewide config.yml. While this opens up all the configurable parts of Markdown Extra, my original goal of making code blocks play with Google Prettify is achieved by adding this to config.yml
Using this I can format code in Markdown with fenced code blocks which also hint at the syntax to be used
Markdown will render that with
<pre class="prettyprint lang-js"><code>...</code></pre>
and the Google Prettify script will play nicely with it.